Method for registering customized device, server, and terminal

ABSTRACT

A method is provided. The method includes receiving a device type identifier, network access data, and a user identifier that correspond to an order identifier from a terminal. An allocated device serial number corresponding to the order identifier is obtained, the device type identifier, the device serial number, the network access data being written into a customized controlled device. The customized controlled device that is identified by the allocated device serial number and the device type identifier is connected to. A device registration request is received from the terminal and, in response to receiving the device registration request, device registration is performed based on the device type identifier, the allocated device serial number, and the user identifier.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. patentapplication Ser. No. 16/033,360, filed Jul. 12, 2018, which is acontinuation of International Application No. PCT/CN2017/083022, filedon May 4, 2017, which claims priority from Chinese Patent ApplicationNo. 201610304057.x, entitled “METHOD FOR REGISTERING CUSTOMIZED DEVICEAND APPARATUS” filed on May 9, 2016, in the Chinese Patent Office, thedisclosures of which are incorporated herein by reference in theirentireties.

BACKGROUND 1. Field

This application relates to methods for registering a customized device,a server, and a terminal, in the field of Internet technologies.

2. Description of Related Art

The Internet of Things is an important part of the new generation ofinformation technologies, which refers to an internet in which thingsare connected to each other. A core and a basis of the Internet ofThings are still the Internet. The Internet of Things is a networkextended and expanded based on the Internet. The Internet of Thingsenables the Internet based on a terminal to be extended and expanded toinformation exchange and communication between a terminal and a thing,and between things.

In the related art, device production vendors can build a network accessmodule in devices such as a socket, a camera, an air conditioner, arefrigerator, and a watch, to produce a controlled device that can beconnected to a network. After purchasing the controlled device, a userneeds to perform a device registration operation, and establish anassociation between the user and the controlled device to access andcontrol the controlled device.

A controlled device needs to be registered for use, on the premise thatthe controlled device accesses a network. In the related art, when acontrolled device needs to access a network, a user needs to manuallyfill in the data needed for network access. For example, a user needs tomanually enter a service set identifier (SSID) and a password. Therelated art technology is inconvenient and inefficient to the user toregister the controlled device through the network, resulting in lowefficiency for registering the controlled device.

SUMMARY

According to an aspect of one or more exemplary embodiments, there isprovided a method including receiving a device type identifier, networkaccess data, and a user identifier that correspond to an orderidentifier from a terminal. An allocated device serial numbercorresponding to the order identifier is obtained, the device typeidentifier, the device serial number, the network access data beingwritten into a customized controlled device. The customized controlleddevice that is identified by the allocated device serial number and thedevice type identifier is connected to. A device registration request isreceived from the terminal and, in response to receiving the deviceregistration request, device registration is performed based on thedevice type identifier, the allocated device serial number, and the useridentifier.

According to an aspect of one or more exemplary embodiments, there isprovided a method performed by at least one computer processor, themethod comprising obtaining an order identifier, and uploading a devicetype identifier, network access data, a user identifier, and the orderidentifier correspondingly to a server, the device type identifier, thenetwork access data, and an allocated device serial number correspondingto the order identifier being written into a customized controlleddevice. A device registration request is sent to the server. A deviceregistration result is received from the server.

According to an aspect of one or more exemplary embodiments, there isprovided a server comprising at least one memory configured to storecomputer program code and at least one processor configured to accessthe at least one memory and operate according to the computer programcode. The computer program code includes code to implement receiving adevice type identifier, network access data, and a user identifier thatcorrespond to an order identifier from a terminal. An allocated deviceserial number corresponding to the order identifier, the device typeidentifier, the device serial number is obtained, the network accessdata being written into a customized controlled device. The customizedcontrolled device that is identified by the allocated device serialnumber and the device type identifier is connected to. A deviceregistration request is received from the terminal and, in response toreceiving the device registration request, device registration isperformed based on the device type identifier, the allocated deviceserial number, and the user identifier.

According to an aspect of one or more exemplary embodiments, there isprovided a terminal comprising at least one memory configured to storecomputer program code and at least one processor configured to accessthe at least one memory and operate according to the computer programcode. The computer program code includes code to implement obtaining anorder identifier, and uploading a device type identifier, network accessdata, a user identifier, and the order identifier correspondingly to aserver, the device type identifier, the network access data, and anallocated device serial number corresponding to the order identifierbeing written into a customized controlled device. A device registrationrequest is sent to the server and a device registration result isreceived from the server.

The details of one or more exemplary embodiments are provided in theaccompanying drawings and descriptions below. Other features,objectives, and advantages of this application become more obvious byreferencing the specification, accompanying drawings, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings described herein are used for providingfurther understanding for this application and constitute a part of thisapplication. Example embodiments of this application and descriptionsthereof are used for explaining this application and do not constitutean improper limitation to this application. In the drawings,

FIG. 1 is a diagram of an application environment of a system formanaging a customized device according to an exemplary embodiment;

FIG. 2 is a schematic structural diagram of a server used as an Internetof Things (IoT) open platform according to an exemplary embodiment;

FIG. 3 is a schematic structural diagram of a terminal according to anexemplary embodiment;

FIG. 4 is a schematic flowchart of a method for registering a customizeddevice according to an exemplary embodiment;

FIG. 5 is a schematic flowchart of a method for registering a customizeddevice according to another exemplary embodiment;

FIG. 6 is a schematic diagram of an unregistered-device informationquery portal in a social application according to an exemplaryembodiment;

FIG. 7 is a schematic diagram of an unregistered-device informationquery portal in a social application according to an exemplaryembodiment;

FIG. 8 is a schematic diagram of a registered-device information queryportal in a social application according to an exemplary embodiment;

FIG. 9 is a schematic flowchart of a method for registering a customizeddevice according to an exemplary embodiment;

FIG. 10 is a structural block diagram of a server according to anexemplary embodiment;

FIG. 11 is a structural block diagram of a server according to anexemplary embodiment;

FIG. 12 is a structural block diagram of a terminal according to anexemplary embodiment; and

FIG. 13 is a structural block diagram of a terminal according to anexemplary embodiment.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

The following describes exemplary embodiments of the present disclosurein detail with reference to the accompanying drawings. It should beunderstood that, the following described exemplary embodiments aremerely used to describe and explain the present disclosure, and are notused to limit the present disclosure. It should note that the exemplaryembodiments to be described are some rather than all of the exemplaryembodiments of this application. All other embodiments obtained by aperson skilled in the art based on the example embodiments of thepresent application without creative efforts shall fall within theprotection scope of the present application.

FIG. 1 is a diagram of a system for managing a customized deviceaccording to an exemplary embodiment. The system may include an IoT openplatform 110, a terminal 120, a device customization server 130, and alogistics server 140. The system for managing a customized device isconfigured to provide a customization and access service to a controlleddevice 150. The IoT open platform 110 includes one or more servers, isconfigured to provide an access service to the controlled device 150,and interacts with the terminal 120, the device customization server130, and the logistics server 140. The IoT open platform 110 isconfigured to process the device registration request. The terminal 120,for example, a terminal 120 (1) and a terminal 120 (2) shown in FIG. 1 ,is configured to perform device registration on the controlled device150, access the controlled device 150, and the like by means of the IoTopen platform 110. The device customization server 130 is configured tocontrol customization steps such as production and data write of thecontrolled device 150. The logistics server 140 is configured to processlogistics information related to the controlled device 150.

FIG. 2 is a schematic structural diagram of a server that can be used asIoT open platform according to an exemplary embodiment. The server mayinclude a processor, a non-transitory computer storage medium, a memory,and a network interface that are connected by using a system bus. Thenon-transitory computer storage medium stores an operating system andcomputer readable instructions, and when executed by the processor, thecomputer readable instructions can cause the processor to perform amethod for registering a customized device. The memory stores computerreadable instructions, and when executed by the processor, the computerreadable instructions can cause the processor to perform a method forregistering a customized device. The network interface is configured toconnect to a network.

FIG. 3 is a schematic structural diagram of a terminal according to anexemplary embodiment. The terminal may include a processor, anon-transitory computer storage medium, a memory, a network interface, adisplay screen, a camera, and an input apparatus that are connected byusing a system bus. The non-transitory computer storage medium stores anoperating system and computer readable instructions, and when executedby the processor, the computer readable instructions can cause theprocessor to perform a method for registering a customized device. Thememory stores computer readable instructions, and when executed by theprocessor, the computer readable instructions can cause the processor toperform a method for registering a customized device. The networkinterface is configured to connect to a network. The display screen maybe a liquid crystal display screen or an electronic ink display screen,or the like. The input apparatus may be a touchpad, a track ball, amouse, or a touch layer overlapping the display screen, a touchscreenwhich form by the display screen and the touch layer, or the like. Thenetwork interface is configured to connect to a network. The terminalmay be a personal computer or a mobile terminal or the like. The mobileterminal includes at least one of a mobile phone, a tablet computer, apersonal digital assistant (PDA), an ebook reader that can be connectedto a network, and the like.

FIG. 4 is a schematic flowchart of a method for registering a customizeddevice according to an exemplary embodiment. In this exemplaryembodiment, the descriptions are made by using that the method isapplied to the foregoing IoT open platform. For example, the IoT openplatform 110 shown in the FIG. 1 . The method may include the followingsteps:

Step 402: Receive a device type identifier, network access data, and auser identifier that are corresponding to an order identifier and thatare uploaded by the terminal.

The order identifier is a unique identifier of an order. An orderrepresents a task of customizing a controlled device. The order mayinclude the device type identifier representing a type of the customizedcontrolled device, the network access data, a user identifier of anactual user representing the controlled device, or the like. The networkaccess data is data needed for accessing a network, for example, a BSSIDand a corresponding password of a router in the user's house, or anetwork dial account and a corresponding password. There may be multiplepieces of network access data. The user identifier is a unique stringfor identifying the user. The user may customize appearance, package,embedded-in software content, the like of the controlled device, andother than the network access data of the controlled device. Customizedcontent is corresponding to the order identifier.

In an exemplary embodiment, the IoT open platform may receive an ordercreation request triggered by the terminal, generate an order identifierbased on the order creation request and return the order identifier tothe terminal, and then receive device type identifier, network accessdata, and a user identifier that are corresponding to the orderidentifier and that are uploaded by the terminal.

In an exemplary embodiment, the IoT open platform may receive an ordercreation request triggered by a first terminal, and generate an orderidentifier according to the order creation request and return the orderidentifier to the first terminal, so that the first terminal transfersthe order identifier and a selected device type identifier to a secondterminal. Then, the IoT open platform receives the device typeidentifier, network access data, and a user identifier that arecorresponding to the order identifier and that are uploaded by thesecond terminal. The user identifier in this exemplary embodiment is auser identifier of the second terminal.

Specifically, the first terminal may transfer a link that is generatedbased on the order identifier and the selected device type identifier tothe second terminal; or the first terminal may display a graphic code,the graphic code being formed by encoding the link that is generatedaccording to the order identifier and the selected device typeidentifier, and the second terminal scan and parse the displayed graphiccode, to obtain the order identifier and the device type identifier. Ato-be-invoked program may be specified in the link. Therefore, when thesecond terminal clicks the link, the corresponding program can bedirectly invoked. Then, the device type identifier, the network accessdata, and the user identifier that are corresponding to the orderidentifier is uploaded by using the program. The graphic code may be,for example, a two-dimensional code or a barcode. The link may betransferred by using an instant message, an SMS message, or the like.The link may be generated by the IoT open platform. The graphic code maybe generated by the IoT open platform or the terminal.

Step 404: Obtain an allocated device serial number corresponding to theorder identifier, the device type identifier, the device serial number,and the network access data being written into a customized controlleddevice.

Specifically, the IoT open platform may allocate, directly or by usinganother server, the device serial number corresponding to the orderidentifier, store a correspondence between the order identifier, thedevice type identifier, the device serial number, and the useridentifier, and write, directly or by using another server, the devicetype identifier, the device serial number, and the network access datainto the customized controlled device. The IoT open platform maysynchronously send the device serial number to the terminal. The orderidentifier may further correspond to a quantity of the customizedcontrolled devices. Therefore, the allocated device serial number isconsistent with the quantity of the controlled devices.

The network access data written into the controlled device is used toconnect the controlled device to a network after the controlled deviceis powered on. The written-in device type identifier and the deviceserial number constitute a unique identifier of the controlled device,so that the controlled device may access, after being connected to thenetwork, the IoT open platform according to the device type identifierand the device serial number.

In an exemplary embodiment, step 404 may include sending the orderidentifier, the network access data, and/or the device type identifierto a device customization server, so that the device customizationserver allocates the device serial number corresponding to the orderidentifier, and writes the device type identifier, the device serialnumber, and the network access data into the customized controlleddevice; and receiving the device serial number that is corresponding tothe order identifier and that is fed back by the device customizationserver.

Specifically, the device customization server may be a serverestablished by a device vendor to control automatic production processessuch as manufacturing and installation of the controlled device. Whenneeding to customize a controlled device, the user may submit an orderto the IoT open platform. The IoT open platform controls an automaticproduction process of the controlled device by using the devicecustomization server, allocates a device serial number to the customizedcontrolled device, and writes a device type identifier, the deviceserial number, and network access data into the customized controlleddevice. Certainly, other customized content may also be written into thecustomized controlled device. The device customization server returnsthe allocated device serial number to the IoT open platform. The IoTopen platform stores the device serial number corresponding to the orderidentifier, and returns the device serial number to the terminal.

Step 406: Connect to the controlled device that accesses a networkaccording to the network access data and that is identified by using thedevice serial number and the device type identifier.

Specifically, after being powered on, the controlled device may beconnected to the network according to the written-in network accessdata. For example, a written-in BSSID is searched for, and a networkaccess request carrying a written-in password of the controlled deviceis sent to a router broadcasting the BSSID, so that the routerestablish, after password authentication is successful, a networkconnection to the controlled device, and the controlled device accessesthe network.

After accessing the network successfully, the controlled device sends anaccess request carrying the device type identifier, the device serialnumber, and a network address corresponding to the controlled device tothe IoT open platform, so that the IoT open platform establishes aconnection to the controlled device based on the access request, andrecords a correspondence between the device type identifier, the deviceserial number, and the network address. The IoT open platform mayperform authentication according to the device type identifier and thedevice serial number that are carried in the access request. If theauthentication is successful, the access request of the controlleddevice is accepted, and a connection to the controlled device isestablished.

Step 408: Receive a device registration request from the terminal.

Step 410: Perform device registration based on the device typeidentifier, the device serial number, and the user identifier.

Specifically, the IoT open platform may receive a device registrationrequest carrying an order identifier, so as to obtain a device typeidentifier, a device serial number, and a user identifier correspondingto the order identifier, and performs device registration according tothe obtained device type identifier, the device serial number, and theuser identifier. Device registration is mainly to establish anassociation between a controlled device and a user, so that a user thatcompletes device registration has a right of controlling a correspondingcontrolled device.

In an exemplary embodiment, the IoT open platform may receive a deviceregistration request carrying a device type identifier, a device serialnumber, and a user identifier, and perform device registration accordingto the carried device type identifier, the device serial number, and theuser identifier.

In an exemplary embodiment, the IoT open platform may receive a deviceregistration request carrying an order identifier, a device typeidentifier, a device serial number, and a user identifier, and checkwhether the carried device type identifier, the device serial number,and the user identifier are consistent with a device type identifier, adevice serial number, and a user identifier that are carried in theorder identifier. If a check result is that the carried device typeidentifier, the device serial number, and the user identifier areconsistent with a device type identifier, a device serial number, and auser identifier that are carried in the order identifier, deviceregistration is performed according to the carried device typeidentifier, the device serial number, and the user identifier.

By means of the foregoing method for registering a customized device, auser can customize a controlled device, write network access data usedfor accessing a network into the customized controlled device, and writea device type identifier and a device serial number that are used foridentifying the controlled device into the customized controlled device.In this way, when the controlled device is in an application scenario inwhich the written-in network access data is used for accessing anetwork, the controlled device may access the network automaticallyaccording to the network data and is connected to a device registrationserver, thereby improving network access efficiency. The user only needsto trigger a device registration request to enable device registrationto be automatically completed, thereby improving device registrationefficiency.

In an exemplary embodiment, the receiving a device type identifier,network access data, and a user identifier that are corresponding to anorder identifier and that are uploaded by a terminal includes: receivingan order creation request triggered by a first terminal; generating anorder identifier according to the order creation request and returningthe order identifier to the first terminal, so that the first terminaltransfers the order identifier and a selected device type identifier toa second terminal; and receiving the device type identifier, networkaccess data, and a user identifier that are corresponding to the orderidentifier and that are uploaded by the second terminal; and thereceiving a device registration request from the terminal includes:receiving a device registration request from the second terminal. Inthis exemplary embodiment, the first terminal can help the secondterminal to process a order, to generate data for device registration,and the second terminal completes device registration, thereby furtherimproving convenience of device registration.

In an exemplary embodiment, the method for registering a customizeddevice further includes: receiving an order cancellation request fromthe terminal; and sending the order cancellation request to a devicecustomization server, so that the device customization server clears thedevice type identifier, the device serial number, and the network accessdata that are written into the controlled device and that are specifiedin the order cancellation request.

Specifically, after receiving a customized controlled device, a user maydecide whether to return the customized controlled device according tohis or her requirement. If deciding to return the customized controlleddevice, the user sends the controlled device back to a vendor, and sendsan order cancellation request by using the terminal. The terminal sendsthe order cancellation request to the IoT open platform. The IoT openplatform sends the order cancellation request to a device customizationserver. Then, the device customization server clears data in thecontrolled device specified in the order cancellation request, to deletenetwork access data written into the controlled device, or clears all ofa device type identifier, a device serial number, and the network accessdata that are written into the controlled device. The order cancellationrequest may carry an order identifier, or may carry a user identifier,or may carry a device type identifier and a device serial number, tospecify the controlled device.

In this exemplary embodiment, a user may return a controlled deviceaccording to a requirement. A vendor may clear data in a returnedcontrolled device in time, to delete customized content, andsubsequently, may write customized content into the controlled deviceagain in response to a customization requirement of another user, sothat it is convenient to recycle the controlled device, thereby savingresources. For the IoT open platform and the device customizationserver, a task of customizing a controlled device is identified by usingan order identifier, and user information will not be leaked.

In an exemplary embodiment, step 410 may include: generating a deviceaccount according to the device type identifier, the device serialnumber, and the user identifier; and sending the device account to thecontrolled device.

Specifically, the device account may include at least one of a number, aletter, and punctuation, and can uniquely identify a correspondingcontrolled device. After generating a device account, the IoT openplatform sends the device account to a controlled device, so that thecontrolled device subsequently accesses an IoT open platform by usingthe device account. The IoT open platform sends the device account to aterminal, so that the terminal can subsequently access the controlleddevice by using device account. After generating the device account, theIoT open platform stores a correspondence between the device account,the user identifier, the device type identifier, and the device serialnumber. The IoT open platform may subsequently determine, according tothe correspondence, the device account of the controlled device that isidentified by the device type identifier and the device serial number,and determine a right that is of the corresponding user identifier andthat is of controlling the controlled device.

In an exemplary embodiment, the IoT open platform may obtaincorresponding signature data according to a device type identifier and adevice serial number, and generate a device account according to theuser identifier, the device type identifier, and the signature data. Thesignature data is corresponding to both the device type identifier andthe device serial number. The signature data may be used to authenticatevalidity of a device type identifier and/or a device serial numbercarried in a registration request. In an exemplary embodiment, thesignature data is generated by encrypting the device serial number. Anencryption algorithm may be, for example, a message digest algorithm 5(MD5).

In an exemplary embodiment, the IoT open platform may generate a new andunique device account, and record an association between the deviceaccount and a user identifier, a device type identifier, and signaturedata. The association indicates that the unique device account isgenerated according to the corresponding user identifier, device typeidentifier, and signature data.

In an exemplary embodiment, the IoT open platform may obtain a string bycombining a user identifier, a device type identifier, and signaturedata, so as to generate a device account according to the stringobtained by combination. To generate a device account according to thestring obtained by combination, specifically, the string obtained bycombination may be directly used as a device account, or the stringobtained by combination may be mapped, by means of a hash algorithm,into a unique device account with a fixed length.

In an exemplary embodiment, the IoT open platform may performauthentication according to signature data. If the authentication issuccessful, a device account is generated according to a user identifierand a device type identifier, or a device account is generated accordingto the user identifier, the device type identifier, and the signaturedata after the authentication is successful; or if the authentication isnot successful, a result that device registration is a failure isreturned to a terminal.

In an exemplary embodiment, the IoT open platform may decrypt signaturedata to obtain a device serial number, and compares the device serialnumber obtained by means of decryption with a device serial numberextracted from a device registration request. If the device serialnumber obtained by means of decryption is consistent with the deviceserial number extracted from a device registration request,authentication is successful; or if the device serial number obtained bymeans of decryption is not consistent with the device serial numberextracted from a device registration request, authentication is afailure.

In an exemplary embodiment, the method for registering a customizeddevice further includes: obtaining a tracking number associated with theorder identifier; obtaining logistics information corresponding to thetracking number; and sending the logistics information to the terminalaccording to the user identifier corresponding to the order identifier.

Specifically, after writing data into a controlled device, a vendor maydeliver the controlled device to a logistics company, and the logisticscompany transports the controlled device to a location of a user. Thelogistics company generates corresponding tracking number when receivinga task of transporting the controlled device. A device customizationserver associates the tracking number with an order identifier, andsynchronously sends the association to the IoT open platform.

When receiving a logistics information query request of a terminal, theIoT open platform may obtain an order identifier specified in thelogistics information query request, obtain a tracking number associatedwith the order identifier, actively or passively obtain logisticsinformation that is corresponding to the tracking number and that isfrom a logistics server of the logistics company, and pushes thelogistics information to the terminal.

In this exemplary embodiment, the order identifier is associated with antracking number of the customized controlled device. The IoT openplatform may synchronously send a transportation status of thecustomized controlled device to the terminal, so that the terminal canlearn the transportation status of the customized controlled device intime, thereby improving convenience of the customization,transportation, and use of the controlled device.

As shown in FIG. 5 , in an exemplary embodiment, a method forregistering a customized device is provided. In this exemplaryembodiment, descriptions are made by using that the method is applied tothe foregoing terminal 120 (1) shown in the FIG. 1 an example. Themethod may include the following steps:

Step 502: Obtain an order identifier, and upload a device typeidentifier, network access data, a user identifier, and the orderidentifier correspondingly to a server, the device type identifier, thenetwork access data, and an allocated device serial number correspondingto the order identifier being written into a customized controlleddevice.

The order identifier is an only identifier of an order. An orderrepresents a task of customizing a controlled device. The order includesthe device type identifier representing a type of the customizedcontrolled device, the network access data, and a user identifier of anactual user representing the controlled device. The network access datais data needed for accessing a network, for example, a BSSID and acorresponding password of a router in the user's house, or a networkdial account and a corresponding password. There may be multiple piecesof network access data. The user identifier is a unique string foridentifying the user. The user may customize appearance, package,embedded-in software content, and the like of the controlled device,other than the network access data of the controlled device. Customizedcontent is corresponding to the order identifier.

Specifically, the terminal may access a device customization pageprovided by the IoT open platform, and triggers an order creationrequest and sends the order creation request to the IoT open platform inthe device customization page. Then, the IoT open platform generates anorder identifier and feeds the order identifier back to the terminal,and the terminal receives the order identifier fed back by the IoT openplatform.

In the device customization page, type options of the customizedcontrolled device may be provide. The terminal selects a correspondingtype option according to a user operation, and obtains a device typeidentifier corresponding to the selected type option. The terminal mayobtain network access data entered on the device customization page,obtain a user identifier used for current login, and upload the devicetype identifier, the network access data, the user identifier, and theorder identifier correspondingly to the IoT open platform. The IoT openplatform receives and stores the device type identifier, the networkaccess data, the user identifier, and the order identifier.

In an exemplary embodiment, the terminal may obtain a link, obtain anorder identifier and a device type identifier link that are included inthe link, enter a device customization page according to a link invokingprogram, obtain network access data entered on the device customizationpage, obtain a user identifier used for current login, and upload thedevice type identifier, the network access data, the user identifier,and the order identifier correspondingly to the IoT open platform.

The link may be obtained from a graphic code, an instant message, or anSMS message. The invoked program is a program having functions of deviceregistration and accessing a controlled device, and may be a socialapplication or a dedicated application for controlling a controlleddevice. The social application may include an instant messagingapplication or a social networking service (SNS) application, or thelike. The link may be shared with another terminal, and may be shared byusing a graphic code, an instant message, or an SMS message.

The IoT open platform may allocate, directly or by using another server,the device serial number according to the order identifier, store acorrespondence between the order identifier, the device type identifier,the device serial number, and the user identifier, and write, directlyor by using another server, the device type identifier, the deviceserial number, and the network access data into the customizedcontrolled device. The IoT open platform may synchronously send thedevice serial number to the terminal. The order identifier may furthercorrespond to a quantity of the customized controlled devices.Therefore, the allocated device serial number is consistent with thequantity of the controlled devices.

The network access data written into the controlled device is used toconnect the controlled device to a network after the controlled deviceis powered on. The written-in device type identifier and the deviceserial number constitute a unique identifier of the controlled device,so that the controlled device may access, after being connected to thenetwork, the IoT open platform according to the device type identifierand the device serial number.

In an exemplary embodiment, the device serial number is allocatedcorrespondingly to the order identifier after the device customizationserver receives the order identifier, the network access data, and thedevice type identifier that are sent by the IoT open platform, and thedevice type identifier, the device serial number, and the network accessdata are written by the device customization server into the customizedcontrolled device.

Step 504: Send a device registration request to the server after thecontrolled device accesses a network according to the network accessdata and accesses the server according to the device type identifier andthe device serial number.

Specifically, after being powered on, the controlled device may beconnected to the network according to the written-in network accessdata. For example, a written-in BSSID is searched for, and a networkaccess request carrying a written-in password of the controlled deviceis sent to a router broadcasting the BSSID, so that the routerestablish, after password authentication is successful, a networkconnection to the controlled device, and the controlled device accessesthe network.

After accessing the network successfully, the controlled device sends anaccess request carrying the device type identifier, the device serialnumber, and a network address corresponding to the controlled device tothe IoT open platform, so that the IoT open platform establishes aconnection to the controlled device according to the access request, andrecords a correspondence between the device type identifier, the deviceserial number, and the network address. The IoT open platform mayperform authentication according to the device type identifier and thedevice serial number that are carried in the access request. If theauthentication is successful, the access request of the controlleddevice is accepted, and a connection to the controlled device isestablished.

Step 506: Receive a device registration result that is generated byperforming device registration according to the device type identifier,the device serial number, and the user identifier and that is fed backby the server.

Specifically, the terminal may initiate a device registration requestcarrying an order identifier, and send the device registration requestto the IoT open platform, so that the IoT open platform receives thedevice registration request, obtains a device type identifier, a deviceserial number, and a user identifier that are corresponding to the orderidentifier, and performs device registration according to the obtaineddevice type identifier, device serial number, and the user identifier.Device registration is mainly to establish an association between acontrolled device and a user, so that a user that completes deviceregistration has a right of controlling a corresponding controlleddevice.

In an exemplary embodiment, the IoT open platform may receive a deviceregistration request carrying a device type identifier, a device serialnumber, and a user identifier, and perform device registration accordingto the carried device type identifier, the device serial number, and theuser identifier.

In an exemplary embodiment, the IoT open platform may receive a deviceregistration request carrying an order identifier, a device typeidentifier, a device serial number, and a user identifier, and checkwhether the carried device type identifier, the device serial number,and the user identifier are consistent with a device type identifier, adevice serial number, and a user identifier that are carried in theorder identifier. If a check result is that the carried device typeidentifier, the device serial number, and the user identifier areconsistent with the device type identifier, the device serial number,and a user identifier that are carried in the order identifier, deviceregistration is performed according to the carried device typeidentifier, the device serial number, and the user identifier.

By means of the foregoing method for registering a customized device, auser can customize a controlled device, write network access data usedfor accessing a network into the customized controlled device, and writea device type identifier and a device serial number that are used foridentifying the controlled device into the customized controlled device.In this way, when the controlled device is in an application scenario inwhich the written-in network access data is used for accessing anetwork, the controlled device may access the network automaticallyaccording to the network data and is connected to a device registrationserver, thereby improving network access efficiency. The user only needsto trigger a device registration request to enable device registrationto be automatically completed, thereby improving device registrationefficiency.

In an exemplary embodiment, the terminal may send an order cancellationrequest to the IoT open platform, so that the IoT open platform sendsthe order cancellation request to a device customization server, and thedevice customization server clears the device type identifier, thedevice serial number, and the network access data that are written intothe controlled device and that are specified in the order cancellationrequest.

In an exemplary embodiment, a device registration result carries adevice account generated according to a device type identifier, a deviceserial number, and a user identifier. The method for registering acustomized device may further include: accessing a controlled deviceaccording to the device account by using a server.

Specifically, the device account may include at least one of a number, aletter, and punctuation, and can uniquely identify a correspondingcontrolled device. After generating a device account, the IoT openplatform sends the device account to a controlled device, so that thecontrolled device subsequently accesses the IoT open platform by usingthe device account. The IoT open platform sends the device account to aterminal, so that the terminal can subsequently access the controlleddevice by using the device account. After generating the device account,the IoT open platform stores a correspondence between the deviceaccount, the user identifier, the device type identifier, and the deviceserial number. The IoT open platform may subsequently determine,according to the correspondence, the device account of the controlleddevice that is identified by the device type identifier and the deviceserial number, and determine a right that is of the corresponding useridentifier and that is of controlling the controlled device. Theterminal may request the IoT open platform to deregister a registeredcontrolled device, so that the IoT open platform deregisters acorresponding device account, to unbind the controlled device from auser.

In this exemplary embodiment, after device registration is completed,the terminal is bound to the controlled device. The terminal interactswith the controlled device by means of the device account, so as toavoid leaking the device serial number, thereby ensuring communicationsecurity.

In an exemplary embodiment, the method for registering a customizeddevice may further include: displaying, by using an unregistered-deviceinformation query portal, first device-related information and aregistration widget that are corresponding to the controlled device;triggering the device registration request when a specified operationperformed on the registration widget is detected; and displaying, byusing a registered-device information query portal after the deviceregistration result is received, second device-related information andan access portal that are corresponding to the controlled device.

Specifically, the unregistered-device information query portal is aportal used to query information of a controlled device that already hasan order identifier and that is not registered, for example, a node 602of “my future device” shown in FIG. 6 . The registered-deviceinformation query portal is a portal used to query information of aregistered controlled device, for example, a node 802 of “my device”shown in FIG. 8 . The registration widget is used to trigger a deviceregistration request, and may be in a form of an icon or a text link ora button, for example, a button 604 of “one-click registration and use”shown in FIG. 6 .

After creating an order, a user may query, by using anunregistered-device information query portal 602 of a socialapplication, first device-related information of a controlled devicecorresponding to an order identifier. The first device-relatedinformation is, for example, a device name, a device type identifier, adevice icon, a tracking number, an order identifier, logisticsinformation, or the like. A registration widget 604 may be displayed byusing the unregistered-device information query portal 602.

After receiving the controlled device, the user may click theregistration widget 604 to trigger a device registration request. Afterreceiving a device registration result indicating that registration issuccessful, the terminal clears the first device-related information inthe unregistered-device information query portal 602, as shown in FIG. 7; and displays, by using the registered-device information query portal,second device-related information and an access portal that arecorresponding to the controlled device, as shown in FIG. 8 . The seconddevice-related information is, for example, a device icon, a devicename, an access history, and the like. The access portal is used totrigger to access the controlled device, and may be an icon link or atext link, for example, a link contained in a device icon or a linkcontained in a device name.

In this exemplary embodiment, controlled device-related information isclassified into information before registration and information afterregistration by using different query portals, so that it is convenientfor a user to learn a status of a customized controlled device, and itis quite convenient and rapid to trigger a device registration request,thereby improving convenience of using the controlled device.

As shown in FIG. 9 , in an exemplary embodiment, a method forregistering a customized device is provided, may include the followingsteps:

Step 902: A terminal displays a device customization page provided by anIoT open platform, and sends an order creation request to the IoT openplatform.

Step 904: The IoT open platform generates an order identifier ReNumaccording to the order creation request, feeds the order identifierReNum back to the terminal, and provides type options, that is, PIDoptions of a controlled device that can be customized to the terminal.

Step 906: The terminal performs selection in optional PID optionsaccording to a user operation, obtains a device type identifier PIDcorresponding to a selected PID option, and uploads the device typeidentifier PID and the order identifier ReNum correspondingly to the IoTopen platform, so that the IoT open platform stores the order identifierReNum and the device type identifier PID correspondingly.

Step 908: The terminal obtains the order identifier ReNum and the devicetype identifier PID, invokes a social application to enter a devicecustomization page, obtains a BSSID and a password Pswd that are enteredon the device customization page, obtains a user identifier UserlD usedfor current login, and uploads the BSSID, the password Pswd, and theuser identifier UserlD that are corresponding to the order identifierReNum to the IoT open platform, so that the IoT open platform stores theorder identifier ReNum, the BSSID, the password Pswd, the device typeidentifier PID, and the user identifier UserID correspondingly.

Step 910: The IoT open platform sends the order identifier ReNum, theBSSID, the password Pswd, and the device type identifier PID to a devicecustomization server.

Step 912: The device customization server allocates a device serialnumber SN, and associates the device serial number SN with the orderidentifier ReNum, that is, makes the device serial number SN correspondto the order identifier ReNum.

Step 914: The device customization server writes the BSSID, the passwordPswd, the device type identifier PID, and the device serial number SNinto the customized controlled device.

Step 916: The device customization server synchronously sends theassociation between the device serial number SN and the order identifierReNum to the IoT open platform.

Step 918: The IoT open platform sends the device serial number SN to theterminal corresponding to the user identifier UserlD that iscorresponding to the associated order identifier ReNum.

Step 920: The terminal may query first device-related information suchas the device serial number SN of the controlled device by means of anode of “my future device”.

Step 922: The device customization server associates the orderidentifier ReNum with a tracking number TrackingNum, and synchronouslysends the association to the IoT open platform.

Step 924: A logistics server may send logistics informationcorresponding to the tracking number TrackingNum to the IoT openplatform.

Step 926: The IoT open platform obtains the order identifier ReNumassociated with the tracking number TrackingNum, and pushes, accordingto the order identifier ReNum, the logistics information to thecorresponding terminal.

Step 928: The terminal may query the logistics information of thecustomized controlled device by means of the node of “my future device”.

Step 930: After being powered on, the controlled device accesses anetwork according to the BSSID and the password Pswd written into thecontrolled device.

Step 932: The controlled device sends the device type identifier PID,the device serial number SN, and a network address IPaddr of thecontrolled device to the IoT open platform, so that the IoT openplatform stores a correspondence between the device type identifier PID,the device serial number SN, and the network address IPaddr.

Step 934: The terminal click a registration widget at the node of “myfuture device”, triggers a device registration request carrying a devicetype identifier PID, a device serial number SN, and a user identifierUserlD, and sends the device registration request to the IoT openplatform.

Step 936: The IoT open platform receives the device registrationrequest, extracts the device type identifier PID, the device serialnumber SN, and the user identifier UserlD, and generates a deviceaccount DIN according to the device type identifier PID, the deviceserial number SN, and the user identifier UserlD.

Step 938: The IoT open platform sends the device account DIN to thecontrolled device according to the network address IPaddr correspondingto the device type identifier PID and the device serial number SN.

Step 940: The IoT open platform feeds a device registration resultcarrying the device account DIN back to the terminal.

Step 942: The terminal may query, by means of a node of “my device”,second device-related information of the registered customized device.

Step 944: The terminal may send an order cancellation request to the IoTopen platform.

Step 946: The IoT open platform forwards the order cancellation requestto the device customization server.

Step 948: The device customization server clears, according to the ordercancellation request, the BSSID, the password Pswd, the device typeidentifier PID, and the device serial number SN that are written intothe controlled device.

By means of the foregoing method for registering a customized device, auser can customize a controlled device, write network access data usedfor accessing a network into the customized controlled device, and writea device type identifier and a device serial number that are used foridentifying the controlled device into the customized controlled device.In this way, when the controlled device is in an application scenario inwhich the written-in network access data is used for accessing anetwork, the controlled device may access the network automaticallyaccording to the network data and is connected to a device registrationserver, thereby improving network access efficiency. The user only needsto trigger a device registration request to enable device registrationto be automatically completed, thereby improving device registrationefficiency.

A user may return a controlled device according to a requirement. Avendor may clear data in a returned controlled device in time, to deletecustomized content, and subsequently, may write customized content intothe controlled device again in response to a customization requirementof another user, so that it is convenient to recycle the controlleddevice, thereby saving resources. For the IoT open platform and thedevice customization server, a task of customizing a controlled deviceis identified by using an order identifier, and user information willnot be leaked.

The order identifier is associated with an tracking number of thecustomized controlled device. The IoT open platform may synchronouslysend a transportation status of the customized controlled device to theterminal, so that the terminal can learn the transportation status ofthe customized controlled device in time, thereby improving convenienceof the customization, transportation, and use of the controlled device.

As shown in FIG. 10 , in an exemplary embodiment, a server 1000 isprovided. An internal structure of the server may correspond to thestructure shown in FIG. 2 . All or some of the modules described belowmay be implemented by software, hardware, or a combination thereof. Theserver 1000 includes an order processing module 1001, a device serialnumber processing module 1002, a controlled device connection module1003, and a device registration request processing module 1004.

The order processing module 1001 is configured to receive a device typeidentifier, network access data, and a user identifier that arecorresponding to an order identifier and that are uploaded by aterminal.

The device serial number processing module 1002 is configured to obtainan allocated device serial number corresponding to the order identifier,the device type identifier, the device serial number, and the networkaccess data being written into a customized controlled device.

The controlled device connection module 1003 is configured to: connectto the controlled device that accesses a network according to thenetwork access data and that is identified by using the device serialnumber and the device type identifier.

The device registration request processing module 1004 is configured to:receive a device registration request from the terminal; and performdevice registration according to the device type identifier, the deviceserial number, and the user identifier.

By means of the server 1000, a user can customize a controlled device,write network access data used for accessing a network into thecustomized controlled device, and write a device type identifier and adevice serial number that are used for identifying the controlled deviceinto the customized controlled device. In this way, when the controlleddevice is in an application scenario in which the written-in networkaccess data is used for accessing a network, the controlled device mayaccess the network automatically according to the network data and isconnected to a device registration server, thereby improving networkaccess efficiency. The user only needs to trigger a device registrationrequest to enable device registration to be automatically completed,thereby improving device registration efficiency.

In an exemplary embodiment, the device serial number processing module1002 is further configured to send the order identifier, the networkaccess data, and the device type identifier to a device customizationserver, so that the device customization server allocates the deviceserial number corresponding to the order identifier, and writes thedevice type identifier, the device serial number, and the network accessdata into the customized controlled device; and receive the deviceserial number that is corresponding to the order identifier and that isfed back by the device customization server.

In an exemplary embodiment, the device registration request processingmodule 1004 is further configured to: generate a device accountaccording to the device type identifier, the device serial number, andthe user identifier; send the device account to the controlled device;and send the device account to the terminal.

As shown in FIG. 11 , in an exemplary embodiment, the server 1000 mayfurther include at least one of an order cancellation request processingmodule 1005 and a logistics information processing module 1006.

The order cancellation request processing module 1005 is configured to:receive an order cancellation request from a terminal; send the ordercancellation request to a device customization server, so that thedevice customization server clears a device type identifier, a deviceserial number, and network access data that is written into a controlleddevice and that is specified in the order cancellation request.

The logistics information processing module 1006 is configured to:obtain a tracking number associated with an order identifier; obtainlogistics information corresponding to the tracking number; and send thelogistics information to the terminal according to a user identifiercorresponding to the order identifier.

As shown in FIG. 12 , in an exemplary embodiment, a terminal 1200 isprovided. An internal structure of the terminal 1200 may correspond tothe structure shown in FIG. 3 . All or some of the modules describedbelow may be implemented by software, hardware, or a combinationthereof. The terminal 1200 includes: an uploading module 1201, areceiving module 1202, and a device registration module 1203.

The uploading module 1201 is configured to: obtain an order identifier,and upload a device type identifier, network access data, a useridentifier, and the order identifier correspondingly to a server.

The receiving module 1202 is configured to receive an allocated deviceserial number that is corresponding to the order identifier and that isfed back by the server, the device type identifier, the device serialnumber, and the network access data being written into a customizedcontrolled device.

The device registration module 1203 is configured to: send a deviceregistration request to the server after the controlled device accessesa network according to the network access data and accesses the serveraccording to the device type identifier and the device serial number;and receive a device registration result that is generated by performingdevice registration according to the device type identifier, the deviceserial number, and the user identifier and that is fed back by theserver.

By means of the terminal 1200, a user can customize a controlled device,write network access data used for accessing a network into thecustomized controlled device, and write a device type identifier and adevice serial number that are used for identifying the controlled deviceinto the customized controlled device. In this way, when the controlleddevice is in an application scenario in which the written-in networkaccess data is used for accessing a network, the controlled device mayaccess the network automatically according to the network data and isconnected to a device registration server, thereby improving networkaccess efficiency. The user only needs to trigger a device registrationrequest to enable device registration to be automatically completed,thereby improving device registration efficiency.

In an exemplary embodiment, the device registration result carries adevice account generated according to the device type identifier, thedevice serial number, and the user identifier. As shown in FIG. 13 , theterminal 1200 further includes a device access module 1204, configuredto access the controlled device according to the device account by usingthe server.

As shown in FIG. 13 , in an exemplary embodiment, the terminal 1200further includes an interface management module 1205, configured to:display, by using an unregistered-device information query portal, firstdevice-related information and a registration widget that arecorresponding to a controlled device; trigger a device registrationrequest when a specified operation performed on the registration widgetis detected; and display, by using a registered-device information queryportal after a device registration result is received, seconddevice-related information and an access portal that are correspondingto the controlled device.

In an exemplary embodiment, a server is provided, including a memory anda processor, the memory storing computer readable instructions, and thecomputer readable instructions, when executed by the processor, causingthe processor to perform the following steps: receiving a device typeidentifier, network access data, and a user identifier that arecorresponding to an order identifier and that are uploaded by aterminal; obtaining an allocated device serial number corresponding tothe order identifier, the device type identifier, the device serialnumber, and the network access data being written into a customizedcontrolled device; connecting to the controlled device that accesses anetwork according to the network access data and that is identified byusing the device serial number and the device type identifier; receivinga device registration request from the terminal; and in response to thedevice registration request, performing device registration according tothe device type identifier, the device serial number, and the useridentifier.

In an exemplary embodiment, the receiving a device type identifier,network access data, and a user identifier that are corresponding to anorder identifier and that are uploaded by a terminal includes: receivingan order creation request triggered by a first terminal; generating anorder identifier according to the order creation request and returningthe order identifier to the first terminal, so that the first terminaltransfers the order identifier and a selected device type identifier toa second terminal; and receiving the device type identifier, networkaccess data, and a user identifier that are corresponding to the orderidentifier and that are uploaded by the second terminal; and thereceiving a device registration request from the terminal includes:receiving a device registration request from the second terminal.

In an exemplary embodiment, the obtaining an allocated device serialnumber corresponding to the order identifier includes: sending the orderidentifier, the network access data, and the device type identifier to adevice customization server, so that the device customization serverallocates the device serial number corresponding to the orderidentifier, and writes the device type identifier, the device serialnumber, and the network access data into the customized controlleddevice; and receiving the device serial number that is corresponding tothe order identifier and that is fed back by the device customizationserver.

In an exemplary embodiment, the computer readable instructions, whenexecuted by the processor, further cause the processor to perform thefollowing steps: receiving an order cancellation request from theterminal; and sending the order cancellation request to a devicecustomization server, so that the device customization server clears thedevice type identifier, the device serial number, and the network accessdata that are written into the controlled device and that are specifiedin the order cancellation request.

In an exemplary embodiment, the performing device registration accordingto the device type identifier, the device serial number, and the useridentifier includes: generating a device account according to the devicetype identifier, the device serial number, and the user identifier;sending the device account to the controlled device; and sending thedevice account to the terminal.

In an exemplary embodiment, the computer readable instructions, whenexecuted by the processor, cause the processor to perform the followingsteps: obtaining a tracking number associated with the order identifier;obtaining logistics information corresponding to the tracking number;and sending the logistics information to the terminal according to theuser identifier corresponding to the order identifier.

By means of the foregoing server, a user can customize a controlleddevice, write network access data used for accessing a network into thecustomized controlled device, and write a device type identifier and adevice serial number that are used for identifying the controlled deviceinto the customized controlled device. In this way, when the controlleddevice is in an application scenario in which the written-in networkaccess data is used for accessing a network, the controlled device mayaccess the network automatically according to the network data and isconnected to a device registration server, thereby improving networkaccess efficiency. The user only needs to trigger a device registrationrequest to enable device registration to be automatically completed,thereby improving device registration efficiency.

In an exemplary embodiment, a terminal is provided, including a memoryand a processor, the memory storing computer readable instructions, andthe computer readable instructions, when executed by the processor,causing the processor to perform the following steps: obtaining an orderidentifier, and uploading a device type identifier, network access data,a user identifier, and the order identifier correspondingly to a server,the device type identifier, the network access data, and an allocateddevice serial number corresponding to the order identifier being writteninto a customized controlled device; sending a device registrationrequest to the server after the controlled device accesses a networkaccording to the network access data and accesses the server accordingto the device type identifier and the device serial number; andreceiving a device registration result that is generated by performingdevice registration according to the device type identifier, the deviceserial number, and the user identifier and that is fed back by theserver.

In an exemplary embodiment, the obtaining an order identifier, anduploading a device type identifier, network access data, a useridentifier, and the order identifier correspondingly to a serverincludes: obtaining a link, and obtaining an order identifier and adevice type identifier included in the link; invoking a programaccording to the link, to enter a device customization page; obtainingnetwork access data entered on the device customization page; obtaininga user identifier used for current login; and uploading the device typeidentifier, the network access data, the user identifier, and the orderidentifier correspondingly to the server.

In an exemplary embodiment, the device registration result carries adevice account generated according to the device type identifier, thedevice serial number, and the user identifier; and the computer readableinstructions, when executed by the processor, further cause theprocessor to perform the following step: accessing the controlled deviceby using the server according to the device account.

In an exemplary embodiment, the computer readable instructions, whenexecuted by the processor, cause the processor to perform the followingsteps: displaying, by using an unregistered-device information queryportal, first device-related information and a registration widget thatare corresponding to the controlled device; triggering the deviceregistration request when a specified operation performed on theregistration widget is detected; and displaying, by using aregistered-device information query portal after the device registrationresult is received, second device-related information and an accessportal that are corresponding to the controlled device.

By means of the foregoing terminal, a user can customize a controlleddevice, write network access data used for accessing a network into thecustomized controlled device, and write a device type identifier and adevice serial number that are used for identifying the controlled deviceinto the customized controlled device. In this way, when the controlleddevice is in an application scenario in which the written-in networkaccess data is used for accessing a network, the controlled device mayaccess the network automatically according to the network data and isconnected to a device registration server, thereby improving networkaccess efficiency. The user only needs to trigger a device registrationrequest to enable device registration to be automatically completed,thereby improving device registration efficiency.

A person of ordinary skill in the technology may understand that all orsome of the processes of the methods in the exemplary embodiments may beimplemented by a computer program that instructs relevant hardware. Thecomputer program may be stored in a computer readable storage medium.When the program runs, the processes of the methods in the exemplaryembodiments are performed. The storage medium may be a non-volatilestorage medium such as a magnetic disk, an optical disc, or a read-onlymemory (ROM), or may be a random access memory (RAM) or the like.

Technical features of the foregoing exemplary embodiments may berandomly combined. To make the description concise, not all possiblecombinations of the technical features in the foregoing exemplaryembodiments are described. However, as long as combinations of thesetechnical features do not contradict each other, it should be consideredthat the combinations all fall within the scope recorded by thisspecification.

The foregoing exemplary embodiments only describe severalimplementations of this application, which are described specificallyand in detail, and therefore cannot be construed as a limitation to thepatent scope of the present application. It should be noted that aperson of ordinary skill in the technology may make various changes andimprovements without departing from the ideas of this application, whichshall all fall within the protection scope of this application.Therefore, the protection scope of the patent of this application shallbe subject to the appended claims.

What is claimed is:
 1. A method performed by at least one computer processor of a server, the method comprising: obtaining a device type identifier, network access data, a user identifier, and an allocated device serial number, corresponding to an order identifier of which generation is triggered by a first terminal, the order identifier identifying an order to customize a controlled device that has not been registered, wherein the device type identifier, the allocated device serial number, and the network access data are written into the customized controlled device; connecting to the customized controlled device that is identified by the allocated device serial number and the device type identifier; receiving, from the first terminal or a second terminal, a device registration request for registering the customized controlled device, the first terminal and the second terminal being different from the controlled device; and in response to receiving the device registration request, performing device registration with the server on the customized controlled device based on the device type identifier, the allocated device serial number, and the user identifier.
 2. The method according to claim 1, wherein the obtaining comprises: receiving an order creation request from the first terminal; generating the order identifier based on the order creation request and transmitting the order identifier to the first terminal; and receiving the device type identifier, the network access data, and the user identifier that correspond to the order identifier from the first terminal or the second terminal.
 3. The method according to claim 1, wherein the obtaining comprises: sending the order identifier, the network access data, and the device type identifier to a device customization server; and receiving the allocated device serial number that corresponds to the order identifier from the device customization server.
 4. The method according to claim 1, further comprising: receiving an order cancellation request from the first terminal or the second terminal; and sending the order cancellation request to a device customization server for clearing the device type identifier, the allocated device serial number, and the network access data that are written into the controlled device and that are specified in the order cancellation request.
 5. The method according to claim 1, wherein the performing the device registration comprises: generating a device account according to the device type identifier, the allocated device serial number, and the user identifier; sending the device account to the controlled device; and sending the device account to the first terminal or the second terminal.
 6. The method according to claim 1, further comprising: obtaining a tracking number associated with the order identifier; obtaining logistics information corresponding to the tracking number; and sending the logistics information to the first terminal or the second terminal according to the user identifier corresponding to the order identifier.
 7. The method according to claim 1, wherein the first terminal is different from the second terminal.
 8. The method according to claim 1, wherein further comprising: in response to receiving an order creation request from the first terminal, providing the order identifier and type options of a device that can be customized to the first terminal; and receiving the device type identifier from the first terminal or the second terminal based on a user operation to select a device option, among the type options, on the first terminal or the second terminal.
 9. The method according to claim 1, further comprising: providing a device customization page to be displayed on the first terminal upon a corresponding application being invoked on the first terminal; and receiving an order creation request, which triggers generation of the order identifier, from the first terminal via the device customization page.
 10. The method according to claim 9, wherein the user identifier is obtained based on a user identifier used for current login of the corresponding application.
 11. A server comprising: at least one memory configured to store computer program code; and at least one processor configured to access the at least one memory and operate according to the computer program code, said computer program code including code to implement: obtaining a device type identifier, network access data, a user identifier, and an allocated device serial number corresponding to an order identifier of which generation is triggered by a first terminal, the order identifier identifying an order to customize a controlled device that has not been registered, wherein the device type identifier, the allocated device serial number, and the network access data are written into a customized controlled device; connecting to the customized controlled device that is identified by the allocated device serial number and the device type identifier; receiving, from the first terminal or a second terminal, a device registration request for registering the customized controlled device, the first terminal and the second terminal being different from the controlled device; and in response to receiving the device registration request, performing device registration on the customized controlled device based on the device type identifier, the allocated device serial number, and the user identifier.
 12. The server according to claim 11, wherein the obtaining comprises: receiving an order creation request from the first terminal; generating the order identifier based on the order creation request and transmitting the order identifier to the first terminal; and receiving the device type identifier, the network access data, and the user identifier that correspond to the order identifier from the first terminal or the second terminal.
 13. The server according to claim 11, wherein the obtaining comprises: sending the order identifier, the network access data, and the device type identifier to a device customization server; and receiving the allocated device serial number that corresponds to the order identifier from the device customization server.
 14. The server according to claim 11, wherein the computer program code further includes code to implement: receiving an order cancellation request from the first terminal or the second terminal; and sending the order cancellation request to a device customization server for clearing the device type identifier, the allocated device serial number, and the network access data that are written into the controlled device and that are specified in the order cancellation request.
 15. The server according to claim 11, wherein the performing the device registration comprises: generating a device account according to the device type identifier, the allocated device serial number, and the user identifier; sending the device account to the controlled device; and sending the device account to the first terminal or the second terminal.
 16. The server according to claim 11, wherein the computer program code further includes code to implement: obtaining a tracking number associated with the order identifier; obtaining logistics information corresponding to the tracking number; and sending the logistics information to the first terminal or the second terminal according to the user identifier corresponding to the order identifier.
 17. The server according to claim 11, wherein the computer program code further includes code to implement: in response to receiving an order creation request from the first terminal, providing the order identifier and type options of a device that can be customized to the first terminal; and receiving the device type identifier from the first terminal or the second terminal based on a user operation to select a device option, among the type options, on the first terminal or the second terminal.
 18. The server according to claim 11, wherein the computer program code further includes code to implement: providing a device customization page to be displayed on the first terminal upon a corresponding application being invoked on the first terminal; and receiving an order creation request, which triggers generation of the order identifier, from the first terminal via the device customization page.
 19. The server according to claim 18, wherein the user identifier is obtained based on a user identifier used for current login of the corresponding application.
 20. A non-transitory computer-readable storage medium having stored therein a computer readable code executable by a processor to perform: obtaining a device type identifier, network access data, a user identifier, and an allocated device serial number, corresponding to an order identifier of which generation is triggered by a first terminal, the order identifier identifying an order to customize a controlled device that has not been registered, wherein the device type identifier, the allocated device serial number, and the network access data are written into the customized controlled device connecting to the customized controlled device that is identified by the allocated device serial number and the device type identifier; receiving, from the first terminal or a second terminal, a device registration request for registering the customized controlled device, the first terminal and the second terminal being different from the controlled device; and in response to receiving the device registration request, performing device registration on the customized controlled device based on the device type identifier, the allocated device serial number, and the user identifier. 